Hi we are using Exchange 2003 Enterprise with SP2 ENG (clustered Exchange Server). Sometimes we receive corrupted mails (We try using OWA and Outlook to access, it is also a corrupted mail), we find that if the data in "References" header in mail is too long, the mail may corrupt . I search in the Technote, there is hot fix for Exchange 2000 but not Exchange 2003, anyone have idea on it? thank you very much.

This May also cause if you have any Antivirus/Antispam server before mails get delivered to Exchange. Please make sure that Antivirus/Antispam server not modifying and making it corrupt. There is a hotfix for outlook 2003 http://support.microsoft.com/kb/947350 Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Hi, Whether the hotfix you indicated is KB835259? After searching our internal database, I do not find any similar issue in Exchange 2003. In addition, I have further searched related information regarding the KB835259 in our internal database. I would like to explain that Exchange/Outlook determined whether the message header was ended or not by a space line between the header and the contents. Nevertheless, in Exchange 2000, when the References header is greater than 1000 byte, CRLF is inserted into 998 byte when Exchange 2000 processes the message although CRLF exists already. Therefore CRLF become duplicated and there is a space line between the message headers. Therefore, some headers are missed and the corrupt message issue will occur. The KB947350 provided by Vinod actually limit the References header length to 998. Therefore, currently, it is hard to say whether your issue related to KB835259. Would you please let me know? 1. Whether the issue can be reproduced? If yes, please let me know detailed information regarding how to reproduce the issue. For example, whether the problem message is sent from external sender or internal sender? Whether the issue occurs whether the message is replied by recipients several times? 2. The symptom of the issue. Whether some message body missed of some header information (such as To: CC:) missed 3. Please post the problem message header here for further check 4. If possible, please reproduce the issue and gather the entire message by using Achieve Sink tool. Then, post the message here: How to install and use the Archive Sink utility in Exchange Server 2003 http://support.microsoft.com/kb/871110/en-us Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

1. We cannot reproduced the issue. 2. When the messagebody is corrupted, the subject of the corrupted mail is blank, the header To: and CC: can display correctly 3. We copy the message header from the corrupted mails References: <0013965685A64D2A9BFECF51F89A05CD@LTEDiv3> <009e01ca039b$1e4dcd70$5ae96850$@com> <073b01ca09e7$de4cc930$af64000a@lteeva> <EBB31C7D20724BD089772F14CD26214F@LTEDiv3> <000c01ca0a7a$f4b968c0$de2c3a40$@com> <E7E09D60BC1349D2B465F57BB75087CC@LTEDiv3> <004801ca0a88$d6e96350$84bc29f0$@com> <E560C2F10EEE49949E265AB4AE004413@LTEDiv3> <007a01ca0a93$c110e2a0$4332a7e0$@com> <040101ca0a9f$2f72f020$af64000a@lteeva> <000901ca0aa3$85f7b170$91e71450$@com> <003f01ca0aa9$ac92c0d0$af64000a@lteeva> <1895C399FF0B4EA9AA9FB2905FF33AC2@LTEDiv3> <003f01ca0c0c$4b779730$e266c590$@com> <AD423CEB61305B41B9B39A01F486A0653E3653795C@HKGVMS1.alpha.lftltd.net> <001301ca0ddf$65ae72c0$310b5840$@com> <00c801ca0e5f$51e38e30$af64000a@lteeva> <00d201ca0f58$f4b67f60$de237e20$@com> <0A978EC2E7B1424AADD42C7E29BE6DFF@LTEDiv3> <019b01ca0f60$458bfe40$d0a3fac0$@com> <088f01ca0f6e$6e411a60$af64000a@lteeva> <003301ca0ff6$7e2cb0f0$7a8612d0$@com> <040f01ca1015$1ca6c6d0$af64000a@lteeva> <008401ca1675$537bd6d0$fa7384! 70$@com> This mail view in Outlook, the message body starting with ----------------------------------------------------------------------------70$@com>X-ASG-Orig-Subj: =?xxxxxxxxxxxxxxxxxxxxx?=Subject: =?xxxxxxxxxxxxxxxxxxxxxxxxxx?=Date: Thu, 6 Aug 2009 14:51:18 +0800MIME-Version: 1.0Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_00F1_01CA16A5.5B0BDF00"X-Priority: 3X-MSMail-Priority: NormalX-Mailer: Microsoft Outlook Express 6.00.2900.5512X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512---------------------------------------------------------------------------- We found that there is a common thing in all of the corrupted mails, the body start at 979 words in the References field, in our example, it start at "70$@com" so that we think the corrupted mails is cause by long "References" field in the header

HiThe incomming mails will pass to Barracuda spam firewall and than forward to Exchange server, when we view the source on Barracuda, we find that there is a blank line between<008401ca1675$537bd6d0$fa7384! and 70$@com> So that it will make the mail into corrupted mail? actually we can view the mail content on the Barracuda but not on OWA or Outlook How can we prevent it? We are not sure the blank line is add by the sender or the Barracuda.

Hi, Sorry for delay in response. From your information, I understand that there is a blank line between 008401ca1675$537bd6d0$fa7384! and 70$@com. I believe that is why the message corrupted in Exchange/Outlook. As I explained in my previous post, the Exchange determined whether the message header was ended or not by a space line between the header and the contents. Therefore, in your case, Exchange considers the 70$@com and later message header information (subject and so on) are part of the message content. According to RFC 2822, it has description below: http://www.faqs.org/rfcs/rfc2822.html A message consists of header fields (collectively called "the header of the message") followed, optionally, by a body. The header is a sequence of lines of characters with special syntax as defined in this standard. The body is simply a sequence of characters that follows the header and is separated from the header by an empty line (i.e., a line with nothing preceding the CRLF). In addition, from your description, I understand that the message format is already incorrect before the message is submitted to Exchange Server. At this time, the issue either occurs on the Barracuda side or the sender side. As the issue cannot always be reproduced, would you please let me know whether all the problem messages are sent from external sender? If yes, please also check whether the problem messages are sent from a specific external sender (or domain). If the problem messages are sent from a specific external sender (or domain), I suspect that the issue related to sender side. In addition, I suggest you have the external send to resend the same message to check whether the issue can be reproduced. If the issue can be reproduced, please capture a network package before the message submitted to Barracuda. Then, please check whether the CRLF already exists. Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com